home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
status10.zip
/
STATUS.DOC
< prev
next >
Wrap
Text File
|
1992-10-03
|
7KB
|
152 lines
Network Mail STATUS
=================================================================
This program generates an network import mail status
bulletin showing each conference, 1000 maximum, and the total
number of messages to date per conference, the last import date
and the total messages to date for the specified network. This
program uses Postlink's export/import log(s).
This archive should contain the following files:
STATUS.EXE STATUS.DOC READ.ME STATUS.BAT
STATUS.EXE is the actual program, STATUS.DOC should be this
file, READ.ME contains any update/changes information, STATUS.BAT
is a sample batch file showing various ways the program can be
used.
If you find this program useful please send $7.50. If you
don't like it please write to me and explain why. Send me any
suggestions you might have and tell me about them. If they
enhance the overall program I will try incorporate part/some/all
in the next release. I just put too much time into this program
to release it as freeware like I did my Lasttime program.
It was my own idea not to include export information since
some sysops might use it as a club to beat over the heads of
their users for not sending out very many messages. I also did
not want to see anyone offended, user or sysop, by the lack of
outgoing messages. If enough people want an export bulletin
generated I will make a separate bulletin generator/program for
this.
Syntax is pretty straight forward:
STATUS Postlink C:\POSTLINK.LOG C:\PCB\GEN\BLT7 [ANSI[ASCII]]
"Postlink" is the actual name of the network you are using,
one word and is case sensitive. 14 characters max, longer names
may cause line wrap on the second line of the bulletin. Say you
are making two different network mail runs with the same
software, you would use those names here.
"C:\POSTLINK.LOG" is the path to you Postlink log(s).
"C:\PCB\GEN\BLT7" is the path and name for your bulletin.
"ANSI" means colorizing and no IBM extended graphic
characters. "ASCII" means no colorizing or IBM extended graphic
characters. Default is "PCB" and means it uses IBM extended
graphic characters and PCBoard's @X0 colorizing codes. If you
leave the fourth parameter blank it defaults to PCB. You do not
need to add "PCB" as a parameter.
"PKZIP.EXE" must be somewhere in your path or in the current
directory. When the month changes in the export/import.log the
program archives the current log into a file using 'ML'+the
current date (ML093092.ZIP, etc.) and writes it out to the
directory that contains the log file. The program then rewrites
the log using only the current new month's data. This way there
is only one month's log data in your postlink's log. If you do
not want the previous month's log simply delete it from your hard
drive. If there are no imported messages on the day of the
rollover then a bulletin reflecting no imported messages is
generated. There must be at least one meg of free disk space for
the archive to be executed. I have no idea the possible sizes and
if anyone has problems with the archive with one meg as the
minimum please let me know and I will increase the size of the
free space needed.
The first three command line options must be populated. All
errors generated in the program are written out to a file called
"STATUS.ERR", which includes the date and time stamp for those
running this in an unattended event. The program first checks the
current directory for STATUS.EXE and this is the default
directory if STATUS.EXE is not in your path.
If you are making two or more DIFFERENT network mail runs
the only thing you must do is make two or more different
POSTLINK.CFG files, one with the name of the LOG file for each
network so that ALL imports are not put into one file. I would
have no way of knowing what network they came form in order to
separate them. You would then just have a TEMP1.CFG, TEMP2.CFG
and when you call postlink you just copy TEMP1.CFG POSTLINK.CFG,
then on next run you might copy TEMP2.CFG POSTLINK.CFG, etc.
A simple batch file might look like one of these:
CD \POSTLINK
COPY TEMP1.CFG POSTLINK.CFG
POSTLINK CALLER.CFG
STATUS Postlink C:\POSTLINK\POSTLINK.LOG C:\PCB\GEN\BLT7 ASCII
CD \POSTLINK
Copy TEMP2.CFG POSTLINK.CFG
POSTLINK CALLER2.CFG
STATUS MyNetwork C:\POSTLINK\MYNET.LOG BLT8 ASCII
Perhaps you want to make a bulletin with the PCBoard @X0
codes in it and one using straight ASCII codes and yet another
using ANSI codes. Here are the three examples:
STATUS Postlink C:\PCB\LOGS\POSTLINK.LOG BLT7G
(bulletin with PCBoard ANSI codes and IBM extended graphic
characters)
STATUS Postlink C:\PCB\LOGS\POSTLINK.LOG BLT7 ASCII
(bulletin in ASCII and no IBM extended graphic characters)
STATUS Postlink C:\PCB\LOGS\POSTLINK.LOG BLT7G ANSI
(bulletin in ANSI colors and no IBM extended graphic
characters)
You just call STATUS as many times as you need to generate
whatever formats you want. A batch file to generate all three
formats might look like this:
ECHO OFF
STATUS Postlink C:\PCB\LOGS\POSTLINK.LOG BLT7 ASCII
STATUS Postlink C:\PCB\LOGS\POSTLINK.LOG BLT7G
STATUS Postlink C:\PCB\LOGS\POSTLINK.LOG BLT77G ANSI
If you need a mail transfer bulletin you might try my
LASTTIME.EXE program. File names are compile dates: LT100392.ZIP
as the current filename/version as of this writing. The versions
dated 092492+ are for the Postlink LASTTIME.TXT file. This format
is different than the one generated by the old PCRelay software
and are not compatible with one another. On top of that
Postlink's LASTTIME.TXT uses some rather strange, to me,
syntax/format.
James Huckabey
3621-A Fraser Street
Bellingham, Washington 98226 U.S.A.
(206) 671-2868 (voice)